Facilitating online to offline commerce

ABSTRACT

Systems and methods for facilitating online to offline commerce are disclosed. In one embodiment, a system configured to receive a request to check-in a customer at a merchant facility is disclosed. The system receives a request to access real-time pre-sale transaction data associated with a first customer and transmits the real-time pre-sale transaction data associated with the first customer to a mobile client device. The request to check-in and the request to access the real-time pre-sale transaction data are transmitted by the first mobile client device. The system is configured to authenticate the request to check-in at the merchant facility, process the request to access the real-time pre-sale transaction data, and responsively access the real-time pre-sale transaction data associated with the first customer from a point of sale device located at the merchant facility.

CLAIM OF PRIORITY

This application claims priority to U.S. Provisional Patent ApplicationNo. 61/444,609 entitled “METHOD, SYSTEM AND APPARATUS FOR FACILITATINGONLINE TO OFFLINE COMMERCE”, which was filed on Feb. 18, 2011, thecontents of which are expressly incorporated by reference herein.

TECHNICAL FIELD

The present disclosure generally relates to the field of commercemanagement and analytics, and in particular, relates to systems,methods, and a machine readable medium for facilitating online tooffline commerce.

BACKGROUND

Businesses like Groupon® and OpenTable® have become increasing popularin recent years. These companies generally facilitate online to offlinecommerce transactions. However, to date, these businesses and otherslike them have focused almost entirely on the consumer and not themerchant. Accordingly, the current nature of consumer titled offeringsprovides modest economic upside for merchants with ever increasingcomplexity.

SUMMARY

Systems and methods for facilitating online to offline commerce aredisclosed. In one embodiment, a system configured to receive a requestto check-in a customer at a merchant facility is disclosed. The systemreceives a request to access real-time pre-sale transaction dataassociated with a first customer and transmits the real-time pre-saletransaction data associated with the first customer to a mobile clientdevice. The request to check-in and the request to access the real-timepre-sale transaction data are transmitted by the first mobile clientdevice. The system is configured to authenticate the request to check-inat the merchant facility, process the request to access the real-timepre-sale transaction data, and responsively access the real-timepre-sale transaction data associated with the first customer from apoint of sale device located at the merchant facility.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a block diagram of an online environment suitable forfacilitating online to offline commerce.

FIG. 2 depicts a block diagram illustrating the components of a hostserver for facilitating online to offline commerce.

FIG. 3 depicts a block diagram illustrating the components of a point ofsale device for facilitating online to offline commerce.

FIGS. 4A-4C depict a flow diagram illustrating an example process forproviding advertising recommendations to affiliated consumers andmerchants.

FIG. 5 depicts a flow diagram illustrating an example process forproviding host server data access to affiliated advertising and/or datamining companies.

FIG. 6 depicts a block diagram of an online environment suitable forfacilitating online to offline commerce.

FIG. 7 depicts a flow diagram illustrating an example process forrequesting real-time pre-sale transaction data via a mobile clientdevice in an online environment suitable for facilitating online tooffline commerce.

FIGS. 8A and 8B depict a flow diagram illustrating example process ofsocial online ordering in an online environment suitable forfacilitating online to offline commerce.

FIG. 9 depicts a sequence diagram illustrating an example of inventorymanagement in an online environment suitable for facilitating online tooffline commerce.

FIGS. 10A-10C depict example user interfaces illustrating the process ofoperating a point of sale device.

FIGS. 11A-10H depict example user interfaces illustrating the process ofonline ordering from the perspective of a mobile client device and apoint of sale device.

FIGS. 12A-12J depict example user interfaces illustrating the process ofchecking in via the in-store experience from the perspective of a mobileclient device and a point of sale device.

FIGS. 13A-13E depict example user interfaces illustrating the process ofsocial online ordering from the perspective of the mobile client devicesand a point of sale device.

FIG. 14 depicts an example user interfaces illustrating a sampleanalytics report displayed on a point of sale device.

FIG. 15 depicts an example user interfaces illustrating the process ofoffline (in-store) ordering from the perspective of the merchant mobiledevices.

FIG. 16 depicts a diagrammatic representation of a machine in theexample form of a computer system within which a set of instructions,for causing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed.

DETAILED DESCRIPTION

The following description and drawings are illustrative and are not tobe construed as limiting. Numerous specific details are described toprovide a thorough understanding of the disclosure. However, in certaininstances, well-known or conventional details are not described in orderto avoid obscuring the description. References to one or an embodimentin the present disclosure can be, but not necessarily are, references tothe same embodiment; and, such references mean at least one of theembodiments.

Reference in this specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the disclosure. The appearances of the phrase “in one embodiment” invarious places in the specification are not necessarily all referring tothe same embodiment, nor are separate or alternative embodimentsmutually exclusive of other embodiments. Moreover, various features aredescribed which may be exhibited by some embodiments and not by others.Similarly, various requirements are described which may be requirementsfor some embodiments but not other embodiments.

The terms used in this specification generally have their ordinarymeanings in the art, within the context of the disclosure, and in thespecific context where each term is used. Certain terms that are used todescribe the disclosure are discussed below, or elsewhere in thespecification, to provide additional guidance to the practitionerregarding the description of the disclosure. For convenience, certainterms may be highlighted, for example using italics and/or quotationmarks. The use of highlighting has no influence on the scope and meaningof a term; the scope and meaning of a term is the same, in the samecontext, whether or not it is highlighted. It will be appreciated thatsame thing can be said in more than one way.

Consequently, alternative language and synonyms may be used for any oneor more of the terms discussed herein, nor is any special significanceto be placed upon whether or not a term is elaborated or discussedherein. Synonyms for certain terms are provided. A recital of one ormore synonyms does not exclude the use of other synonyms. The use ofexamples anywhere in this specification including examples of any termsdiscussed herein is illustrative only, and is not intended to furtherlimit the scope and meaning of the disclosure or of any exemplifiedterm. Likewise, the disclosure is not limited to various embodimentsgiven in this specification.

Without intent to further limit the scope of the disclosure, examples ofinstruments, apparatus, methods and their related results according tothe embodiments of the present disclosure are given below. Note thattitles or subtitles may be used in the examples for convenience of areader, which in no way should limit the scope of the disclosure. Unlessotherwise defined, all technical and scientific terms used herein havethe same meaning as commonly understood by one of ordinary skill in theart to which this disclosure pertains. In the case of conflict, thepresent document, including definitions will control.

Embodiments of the present disclosure include systems, methods, and amachine readable medium for facilitating online to offline commerce. Inone embodiment, a management system and/or a point of sale device,together or separately, facilitate online to offline commerce bydetermining one or more user-specific advertisements to electronicallydeliver to one or more users. The one or more user-specificadvertisements may be designed, for example, to reduce perishableinventory.

In one embodiment, a customer patronizing a merchant and located at themerchant's point of sale or facility can essentially access themerchants system in order to modify and/or pay for goods or services viaa remote management system. For example, a customer can access and viewan itemized pre-sale transaction data (e.g., itemized pre-bill for goodsand/or services) by logging into a remote management system using amobile client device (e.g., a smartphone). In order to facilitate thisonline to offline commerce, the remote management system is incommunication with a point of sale device located at the merchantfacility. The customer can then modify (e.g., buy goods and/or services)and/or pay for goods and/or services using the mobile client device.

In one embodiment, a remote customer (e.g., a user not located at themerchant facility) can log into the management system and access a pointof sale device located at the customer facility in order to modifyand/or pay for goods and/or services for a local customer. To begin, theremote customer may be notified or otherwise identify the location ofthe local customer. For example, the local customer may check in at abar or restaurant via the management system described herein. Themanagement system may then distribute the check-in information tovarious social networking servers (i.e., Facebook®, Twitter®, etc.). Inthis example, the remote customer (e.g., social network friend)identifies that the local customer just checked in at the bar orrestaurant by viewing his or her social news feed (e.g. Facebook® orTwitter® feed). The remote user may then log into the management serverand purchase goods and/or services for the local customer.

In another embodiment, a point of sale device and/or a management systemreceives and manages online purchases. The point of sale device and/ormanagement system, together and/or separately, track the online andoffline orders, merge the online and offline orders, and manage theorders to completion. For example, the management system may managepayment processing in some embodiments.

In another embodiment, a point of sale device and/or a management systemidentifies various virtual business management chains and manages thosevirtual business management chains. For example, the modified point ofsale device and/or management system may together and/or separatelymanage the supply chain, track inventory, manage accounting records,etc.

In one embodiment, the mobile client device and/or the point of saledevice are modified to include additional hardware and or software tofacilitate the online to offline commerce. Additional modifications andfeatures will become evident in view of the following description.

FIG. 1 depicts a block diagram of environment 100 suitable forfacilitating online to offline commerce. Environment 100 includes aplurality of client devices 112A-N, a plurality of merchant point ofsale (POS) devices 122A-N, a plurality of merchant web servers 130A-N, ahost server 140, database repositories 141-143, payments systems 150, aplurality of advertisers 160A-N, a plurality of data miners 170A-N, aplurality of social networks 180A-N, a plurality of applicationdevelopers 185A-N, and network 190.

Host server 140 is configured to communicate with client devices 112A-N,POS devices 122A-N, merchant web servers 130A-N, payments systems 150,advertisers 160A-N, data miners 170A-N, social web servers 180A-N, andapplication developers 185 in order to facilitate online to offlinecommerce as described herein. It is appreciated that the host server 140may also be referred to as a management server.

In one embodiment, the host server 140 facilitates online to offlinecommerce by determining one or more user-specific advertisements toelectronically deliver to the users within environment 100. In oneembodiment, the one or more user-specific advertisements may bedetermined to reduce a merchant's perishable inventory (e.g., foodproducts). In other embodiments, the user-specific advertisements may bedesigned to simply increase traffic or business.

In one embodiment, the host server 140 manages inventory, tracksaccounting information, and can automatically re-order inventory itemswhen necessary. In one example of operation, the host server 140receives a list of inventory items, determines a promotion oradvertisement designed to reduce a specific merchant's inventory items,and electronically provides the promotion to a plurality of consumers.In some embodiments, the consumers may be chosen based on, for example,likelihood of acceptance of the promotion. The host server 140subsequently receives post-sale transaction data indicating acceptanceof the promotion from one or more of the plurality of consumers, andupdates the list of inventory items to reflect the received transactiondata. In this manner the host server 140 can manage inventory items fora merchant. It is appreciated that the post sale transaction data may betransmitted or generated by, for example, a merchant point of saledevice or a merchant web server.

In some embodiments, a user can also log into the host server 140 inorder to interact with “check-in” at an affiliate merchant via amerchant POS device. For example, a user that “checks-in” with amerchant via the host server 140 can be provided with a variety ofinformation. For example, a user can see what they have ordered inreal-time (i.e., pre-bill), can pay via a mobile device, can be providedreal-time coupons, etc.

The plurality of client devices 112A-N can be any systems, devices,and/or any combination of devices/systems that are able to establish aconnection with another device, server and/or other system. The clientdevices 112A-N typically include respective user interfaces 110A-N. Theuser interfaces 110A-N include one or more input devices and a displayor other output functionalities to present data exchanged between thedevices to a user. For example, the client devices can include, but arenot limited to, a server desktop, a desktop computer, a computercluster, a mobile computing device such as a notebook, a laptopcomputer, a handheld computer, a mobile phone, a smart phone, a PDA, aBlackBerry® device, a Treo™, and/or an iPhone or Droid device, etc. Inone embodiment, the client devices 112A-N are coupled to network 190.

In some embodiments, mobile devices of the client devices 112A-N can beconfigured to allow customer's to “check-in” at a merchant locationusing host server 140. These mobile client devices may be configuredwith additional software and/or hardware. For example, a mobile clientdevice 112 may download and run applications (“apps”) that provide forthe communication and functionality described herein. Locationinformation, merchant POS device information, advertisements, analytics,etc., can be exchanged over the communication link established betweenthe mobile client devices 112A-N and the host system 140. In someembodiments, the host server 140 propagates a “check-in” notification toone or more social web servers 180A-N (e.g., Facebook®, Twitter®).

Both mobile and non-mobile users (e.g., a user operating a remote PCclient device) of the social web servers 180A-N may subsequently benotified by the various social web or media servers that the user of themobile client device has “checked-in” at the merchant's location. Themobile and/or non-mobile users of the social web server may be notifiedvia, for example, a social news feed, email, etc. It is appreciated thatin some cases a user may check in at non-merchant locations. Forexample, a user may “check-in” at landmarks or prominent points ofinterest (e.g., the Grand Canyon or the Golden Gate Bridge, etc.). It isappreciated that remote users may purchase other items such as, forexample, admission tickets, souvenirs, etc., at these points ofinterest.

In some embodiments, when users of the social web servers are notifiedthat one or more online friends have checked-in, the users can thenrequest to modify pre-sale transaction data associated with the one ormore online friends that have checked in. For example, a first personmay check-in at a coffee shop in Seattle. The host system 140subsequently sends a check-in notification to one or more of the socialweb servers 180A-N indicating that the first person has checked-in.Alternatively or additionally, the host system 140 sends a request toone or more of the social web servers to check the user in. In oneembodiment, the social web servers 180A-N receive the check-innotification and responsively update the first person's status (e.g., onthe first person's social web feed). One or more of the first person'sonline friends may see the first person's updated status (i.e., that thefirst person checked into a coffee shop in Seattle) and subsequentlypurchase goods and/or services (e.g., a coffee) for the first person.

In one embodiment, the mobile client device of devices 112A-N can beconfigured to communicate with one or more merchant POS devices 122A-Nupon “check-in” at the merchant location. Components of the merchant POSdevices 122A-N are discussed in more detail with respect to FIG. 3. Theplurality of merchant POS devices 122A-N can be any systems, devices,and/or any combination of devices/systems that are able to establish aconnection with network 190 and/or other similar systems. The merchantPOS devices 122A-N typically include respective POS user interfaces120A-N. The POS user interfaces 120A-N include one or more input devicesand a display or other output functionalities to present merchantrelated data. The merchant POS devices 122A-N can include, but are notlimited to, a server desktop, a desktop computer, a computer cluster, amobile computing device such as a notebook, a laptop computer, ahandheld computer, a mobile phone, a smart phone, a PDA, a BlackBerry™device, a Treo™, and/or an iPhone, etc. The POS devices can also includecash drawers, receipt printers, customer displays, barcode scanners,and/or debit/credit card readers and processing systems. In oneembodiment, the POS devices are coupled to network 190.

For offline orders, merchant POS devices 122A-N typically forwardtransaction details (e.g., purchase information) to payment systems 150.This can be done via an SSL encrypted connection to a payment server(not shown for simplicity) hosted by the payment systems 150, forexample. The payment systems 150 can be, for example, payment gateways,payment processors, banks, etc. The payment system 150 are discussed inmore detail with respect to co-pending U.S. patent application Ser. No.13/228,290 entitled “TRACKING OFFLINE COMMERCE AND ONLINE ACTIVITY”,which was filed on Sep. 8, 2011, the contents of which are expresslyincorporated by reference herein.

In some embodiments, one or more of the plurality of POS devices 122A-Ncan be affiliate (e.g., modified) POS devices. Unlike non-affiliate(e.g., un-modified or standard) POS devices, affiliate POS devices cancommunicate with the host server 140 allowing the merchant POS devices122A-N to communicate off-line commerce, employee information, etc.directly to the host server 140. Likewise, an affiliate merchant POSdevice is configured to receive information including on-line orderinformation and customer information from the host system 140. In someembodiments, the merchant POS device tracks and manages all forms datafrom the merchant's business (i.e., all virtual business chains).

The network 190, to which the client devices 112A-N and merchant POSdevices 122A-N are coupled, can be a telephonic network, an opennetwork, such as the Internet, or a private network, such as an intranetand/or the extranet. For example, the Internet can provide filetransfer, remote log in, email, news, RSS, and other services throughany known or convenient protocol, such as, but not limited to the TCP/IPprotocol, Open System Interconnections (OSI), FTP, UPnP, iSCSI, NSF,ISDN, PDH, RS-232, SDH, SONET, etc.

The network 190 can be any collection of distinct networks operatingwholly or partially in conjunction to provide connectivity to the clientdevices 112A-N, merchant POS devices 122A-N, merchant web servers130A-N, payment systems 150, advertisers 160A-N, data miners 170A-N,social web servers 180A-N, and application developers 185A-N. In oneembodiment, communications to and from the client devices 112A-N and toand from the merchant POS devices 122A-N can be achieved by, an opennetwork, such as the Internet, or a private network, such as an intranetand/or the extranet.

The client devices 112A-N and merchant POS devices 122A-N can be coupledto the network (e.g., Internet) via a dial-up connection, a digitalsubscriber loop (DSL, ADSL), cable modem, wireless connections, and/orother types of connection. Thus, the client devices 112A-N cancommunicate with remote servers (e.g., merchant web servers 130A-N, hostservers, mail servers, and/or instant messaging servers, etc.) thatprovide access to user interfaces of the World Wide Web via a webbrowser, for example. Likewise, the merchant POS devices 122A-N cancommunicate with remote servers (e.g., merchant web servers 130A-N, hostservers, and/or gateways, etc.) that provide access to user interfacesof the World Wide Web via a web browser, for example.

The merchant database 141, customer database 142, and advertisements(ads) database 143 can store information such as software, descriptivedata, images, system information, drivers, and/or any other data itemutilized by parts of the host server 140 and/or merchant POS devices foroperation. The merchant database 141, customer database 142, and adsdatabase 143 can be managed by a database management system (DBMS) suchas, but not limited to, Oracle, DB2, Microsoft Access, Microsoft SQLServer, PostgreSQL, MySQL, FileMaker, etc.

The merchant database 141, customer database 142, and advertisements(ads) database 143 can be implemented via object-oriented technologyand/or via text files, and can be managed by a distributed databasemanagement system, an object-oriented database management system(OODBMS) (e.g., ConceptBase, FastDB Main Memory Database ManagementSystem, JDOInstruments, ObjectDB, etc.), an object-relational databasemanagement system (ORDBMS) (e.g., Informix, OpenLink Virtuoso, VMDS,etc.), a file system, and/or any other convenient or known databasemanagement package. As shown, merchant database 141, customer database142, and advertisements (ads) database 143 are coupled to host server140. It is appreciated that, in some embodiments, the merchant database141, customer database 142, and advertisements (ads) database 143 may bealternatively or additionally directly coupled to network 190, merchantPOS devices 122A-N, and/or distributed across multiple systems.

In some embodiments, a set of data or a profile related to a customermay be stored in the customer database 142. For example, a set of datarelated to online and offline purchase history may be stored in customerdatabase 142. Additionally, the customer database 142 may includecustomer preference information, customer account information, paymentinformation, customer social networking information, etc. The customerinformation can be accessed and utilized by the host server 140, forexample, to identify user-specific advertisements and generate reportsuseful to the merchants and/or data miners.

In some embodiments, information related to the various affiliatemerchants is stored in the merchant database 141. The affiliates can bemerchants that provide goods and/or services to consumers, includingusers of client devices 112A-N. For example, affiliates can be onlineretailers, bricks and clicks retailers, and/or traditional brick andmortar retailers. In some embodiments, merchant database 141 can alsoinclude other affiliate specific information such as, for example,inventory data, aggregate and non-aggregate customer data, employeeinformation, menu information, merchant website information, etc. Insome embodiments, the merchant database 141 may also include real-timeinformation related to the merchant that can be shared with a user viaan internet accessible device once the user has “checked-in” using thatdevice. For example, a user that has “checked-in” to a merchant'srestaurant via a web accessible device can view, via the device, whatthe user has ordered in real-time, current deals (e.g., deals of the dayat nearby locations), etc., and electronically pay via the mobile clientdevice.

In some embodiments, a set of data related to advertisers can be storedin the ads database 143. Advertisers 160A-N can access host server 140and submit advertisements that can be later be accessed and used in theconstruction of promotions. For example, the ads may be matched withindividual users based on a customers online and/or offline activity,behavior, and/or customer preferences. In some embodiments, advertisersinclude lead generators such as, for example, Groupon® and Yelp®;although other lead generators are also possible.

In one embodiment, the plurality of data miners 170A-N communicate withthe host system 140 via network 190. The data miners 170A-N include anycompany and/or server that is configured to gather information such as,for example, Google® or Yahoo® servers that gather customer data foranalytics. In one embodiment, the host system provides the data miners170A-N raw data. In some cases, the information provided to the dataminers 170A-N (either through push or pull operations) can be scrubbedof identifying user information. In some cases, customers are asked tosubmit to certain information being shared including but not limited toidentifying customer information.

In one embodiment, a customer (e.g., customer 105) patronizing amerchant and located at the merchant's facility can essentially accessthe merchants point of sale system 120A-N in order to modify and/or payfor goods or services via the host system 140. For example, a customercan access and view an itemized pre-sale transaction data (e.g.,itemized pre-bill for goods and/or services) by logging into orotherwise accessing the host system 140 using a mobile client device112A (e.g., a smartphone). In order to facilitate this online to offlinecommerce, the host system 140 is in communication with a merchant pointof sale device 120A-N located at the merchant facility. The customer canthen modify (e.g., buy goods and/or services) and/or pay for goodsand/or services using the mobile client device 112A.

In one embodiment, a remote customer (e.g., a user not located at themerchant facility) can log into or otherwise access the host system 140and thereby gain access to a merchant point of sale device 120A-Nlocated at the customer facility in order to modify and/or pay for goodsand/or services for social friends, family and/or acquaintances (i.e.local customers). To begin, the remote customer may be notified orotherwise identify the location of a local customer. For example, acustomer may check in at a merchant's facility (e.g., bar or restaurant)via the host server 140 as described herein. The host server 140 maythen distribute the check-in information to various social web servers180A-N (i.e., Facebook®, Twitter®, etc.). In this example, the remotecustomer identifies that the local customer just checked in at the baror restaurant by viewing his or her social information feed (e.g.Facebook® or Twitter® feed. The remote user may then log into the hostserver 140 to buy goods and/or services for the customer that checkedin.

In another embodiment, a merchant point of sale device 120A-N and/or ahost server 140, together and/or separately, receive and/or manageonline purchases for a merchant. The point of sale device 120A-N and/orhost server 140 track the online and offline orders, merge the onlineand offline orders, and manage the orders to completion. In addition,the host server 140 may manage payment processing in some embodimentssuch as crediting the merchant's account, charging the customersaccounts, and/or interfacing with payment system 150.

In another embodiment, a merchant point of sale device 120A-N and/or ahost server 140 systematically identifies various virtual businessmanagement chains and manages those virtual business management chains.For example, the merchant point of sale device 120A-N and/or host server140 may together and/or separately manage the supply chain, trackinventory, manage accounting records, etc.

FIG. 2 depicts a block diagram illustrating an example system 200 thatfacilitates online to offline commerce, according to one embodiment. Thesystem 200 includes host server 140 coupled to a profile database 141,an affiliate database 142, and an ads database 143. As shown, the hostserver 140 is the host server of FIG. 1, although alternativeconfigurations are possible.

The host server 140, although illustrated as comprised of distributedcomponents (physically distributed and/or functionally distributed),could be implemented as a collective element. In some embodiments, someor all of the modules, and/or the functions represented by each of themodules can be combined in any convenient or known manner. Moreover, thefunctions represented by the modules can be implemented individually orin any combination thereof, partially or wholly, in hardware, software,or a combination of hardware and software. Furthermore, it isappreciated that some or all of the host server 140 modules describedwith respect to FIG. 2 may be included, alternatively or additionally,in whole or in part, in the merchant POS device 120 described withrespect to FIG. 3.

In the example of FIG. 2, the host server 140 includes a networkinterface 205, a communication module 208, an administration module 210,a web server module 220, an analytics module 230, a payment processingmodule 240, a social network module 250, a subscription module 255, auser tracking and recording module 260, a data mining module 270, anadvertiser module 280, and a merchant management module 290. Additionalor fewer modules can be included.

The host server 140 can be communicatively coupled to the merchantdatabase 141, and/or the customer database 142, and/or the ads database143, as illustrated in FIG. 2. In some embodiments, the merchantdatabase 141, the customer database 142, and the ads database 143 arepartially or wholly internal to the host server 140. In otherembodiments, the merchant database 141, and/or the customer database142, and/or the ads database 143 are coupled to the host server 140 overnetwork 190. In one or more embodiments, the merchant database 141,and/or the customer database 142, and/or the ads database 143 aredistributed across and/or replicated to both the merchant POS devicesand the host server 140.

In the example of FIG. 2, the network interface 205 can be one or morenetworking devices that enable the host server 140 to mediate data in anetwork with an entity that is external to the server, through any knownand/or convenient communications protocol supported by the host and theexternal entity. The network interface 205 can include one or more of anetwork adaptor card, a wireless network interface card, a router, anaccess point, a wireless router, a switch, a multilayer switch, aprotocol converter, a gateway, a bridge, bridge router, a hub, a digitalmedia receiver, and/or a repeater.

In the example of FIG. 2, the host server 140 includes thecommunications module 208 communicatively coupled to the networkinterface 205 to manage a communication session over a plurality ofcommunications protocols. In one embodiment, the communications module208 receives data (e.g., audio data, textual data, audio files, etc.),information, commands, requests (e.g., text and/or audio-based), and/ortext-based messages over a network. Since the communications module 208is typically compatible with receiving and/or interpreting dataoriginating from various communication protocols, the communicationsmodule 208 is able to establish parallel and/or serial communicationsessions with users of remote client devices, merchant POS devices,payment systems, advertisers, web servers, and data miners.

One embodiment of the host server 140 includes an administration module210. The administration module 210 can be any combination of softwareagents and/or hardware components able to manage and register users ofhost server 140. The administration module 210 includes a registrationengine 212 and an authentication engine 214.

In one embodiment, the registration engine 212 is configured to registernew users, affiliate POS devices, advertisers, and/or applicationdevelopers with the system and/or create new accounts with the hostserver 140. During registration the user can provide login credentialfor the various social networking sites that they would like to log-into or from, and to which the user would like to provide status updatesfrom the host server 140. The authentication engine 214 is configured toauthenticate the host users as they access the host server 140 from avariety of devices. In some embodiments, authentication occurs byassociating a user's username and password with an existing user accountand/or associating an affiliate POS device with an existing affiliateaccount and/or associating an advertiser's username and password with anexisting advertiser account. Unauthorized users, affiliate or merchantPOS devices, and/or advertisers can be directed to register with thesystem. In some embodiments, unauthorized advertisers can be permittedto submit advertisements without registering. However, advertisementsfor these unregistered advertisers may be given less priority.

In some embodiments, advertisers can register for an account so that theadvertisers can provide ads that will be evaluated by host server 140 inorder to provide the users with the one or more user-specificadvertisements. In some embodiments, the advertisers are merchants(i.e., either affiliate or non-affiliate merchants). The host server 140can provide user-specific advertisements to the customers, and thussmall and medium sized businesses or merchants can direct advertisementsto the customers that are most likely to patronize their establishment(off-line and/or online).

One embodiment of the host server 140 includes a web server module 220.The web server module 220 can be any combination of software agentsand/or hardware components able to interact with users that have loggedin or otherwise access or interact with the host server 140. In oneembodiment, the web server module 220 provides access to customers,merchants, advertisers, and/or data miners via a web interface.

In one embodiment, the web server module 220 includes a web engine 222and a mobile web engine 224. As discussed, in some embodiments a usercan access the host server 140 from a mobile client device. The mobileweb engine 224 provides the mobile client device an interface similar tothe interface provided by web engine 222; however, the mobile interfaceis optimized for mobile devices. In some embodiments, the mobile webengine 224 interacts with one or more applications (“apps”) installed onthe mobile client device.

In some embodiments, the web server module 220 presents one or moreuser-specific promotions to a customer through a web portal. The mobileweb portal also allows interaction with a merchant POS device. In otherembodiments, the web server 220 presents one or more merchant-specificpromotion designs or concepts to a merchant via the web portal. Themerchant can view and select appropriate promotions for delivery topotential customers. Promotions may be presented to a user via a printedreceipt from the merchant POS device, electronically via the mobileclient device, and/or electronically via other methods such as, forexample, email.

One embodiment of the host server 140 includes an application developerinterface module 225. The application developer interface module 225 canbe any combination of software agents and/or hardware components able tointerface with application developers. For example, applicationdevelopers can interact with the host server 140 to post/publishapplications on an application exchange system. The applicationdeveloper interface module 225 provides and manages the licensing termsavailable to the application developers, certifies applications uploadedto the host system 140, and makes the applications available fordownload to merchants and/or consumers.

One embodiment of the host server 140 includes an analytics module 230.The analytics module 230 can be any combination of software agentsand/or hardware components able to analyze merchant and/or customerinformation, determine promotions and various other reports to optimizemerchant business chains, employee efficiency, etc., and report theanalytics to the merchant POS and/or data miners. The analytics module230 includes an analysis and optimization engine 232 and a reportingengine 234.

In one embodiment, the analysis and optimization engine 232 processesinformation received from each merchant on an individual basis toprovide the merchants with business performance statistics andoptimization suggestions. However, in some instances, the analysis andoptimization engine 232 may alternatively or additionally processinformation received from a plurality of merchants, aggregate thisinformation, and provide the aggregate information to data miners suchas, for example, Google® or Yahoo®. The analysis and optimization enginecan determine one or more user-specific advertisements based on onlineand offline transaction commerce data.

In one embodiment, the reporting engine 234 stores merchant preferencesregarding the particular types of analytics to be performed includingthe types of business chains on which to perform analytics and how theanalytics should be displayed. For example, a merchant may choose tohave analytics presented related to: sales information, inventoryinformation, customer information, forecast information, employeeinformation, and promotional information. The analytics may be displayedto the merchants in any number of ways. For example, the analytics maybe displayed via a plurality of panes. An example of the various panesthat can be used is illustrated and discussed in more detail withrespect to FIG. 14.

One embodiment of the host server 140 includes a payment module 240. Thepayment module 240 can be any combination of software agents and/orhardware components able to facilitate payment between customers andpayment system 150. The payment module 240 can facilitate payment by andbetween customers, merchants, payment systems, advertisers, data miners,and application developers. The payment module 240 can also manage andtrack accounts for customers, merchants, advertisers, data miners, andapplication developers. For example, the payment module 240 can receivepayment from a remote customer for a friend of the customer's that ischecked-in at a merchant location, pay the merchant for the purchase,and debit the remote customer's account. Debiting the remote customer'saccount may include facilitating payment via payment systems 150.

One embodiment of the host server 140 includes a social network module250. The social network module 250 can be any combination of softwareagents and/or hardware components able to manage customer social networkinformation and status updates/changes. For example, the social networkmodule 250 may process customer status changes (e.g., “check-in” and/or“check-out” indications or requests) and location information receivedfrom mobile device customers, identify one or more of the customer'ssocial networks, and notify the customer's social networks of the statuschanges and/or location information updates.

In one embodiment, the social network module 250 allows customers thatare logged in to the host server to “check-in” with one or more socialnetworking sites such as, for example, Facebook®, FourSquare®, and/orTwitter®. In some cases, a user can directly log-in or “check-in” tomore than one social networking sites via the host server 140. Forexample, a user may “check-in” to a location using the host server andthe host server can then automatically manage the “check-in” status(e.g., “check-in” and “check-out”) at the various social networkingwebsites. Thus, among other features, host server 140 provides a centrallocation for providing status and location information to socialnetworking websites for broadcast to friends via various channels orfeeds.

One embodiment of the host server 140 includes a subscription module255. The subscription module 255 can be any combination of softwareagents and/or hardware components able to manage subscriptions andrewards. The subscription module 255 includes a subscription engine 256and a rewards engine 258.

In one embodiment, the subscription engine 256 manages customersubscriptions. Customers may sign up with the host server 140 for asubscription that entitles the customers to one or more specificbenefits. For example, a customer may pay for a weekly subscription toservices offered via the host server 140 which entitles the customer toa number of VIP meals a week at participating restaurants.

In one embodiment, the loyalty or rewards engine 258 tracks userpurchases at participating or affiliated merchant locations and providesthe users rewards that can be used to purchase goods and/or services atthe participating or affiliated merchant locations. For example, acustomer may frequent an affiliated merchant location and receive rewardpoints on each, visit or based on the number and/or quantity of itemspurchased. The customer may be able to use the reward points to purchasemeals and/or services at affiliate merchants or other merchant locationswhen the reward points meet or exceed a threshold. In some embodiment,the rewards may be redeemable remotely (e.g., to purchase goods and/orservices for an online friend).

When a customer logs into or otherwise accesses the host server 140, thehost server 140 can provide the user with various account and rewardinformation. For example, users may register for an account with thehost server 140 so that the user can log-in or “check-in” to the hostserver and be provided with information such as, for example, electronicreceipts from various affiliate merchants and other benefits including,but not limited to, reward points, promotions, etc.

One embodiment of the host server 140 includes a user tracking andrecording module 260. The user tracking and recording module 260 can beany combination of software agents and/or hardware components able tomonitor or track and store offline and online activity (e.g.,transactions) of a customer. The user activity that can be tracked caninclude, but is not limited to, online researching of a product or amerchant and/or items purchased. In some embodiments, the user activityis analyzed by analytics module to generate user-specific advertisementand/or to determine the likelihood that a consumer would like to receiveinformation about a specific promotion.

In some embodiments, a new user can be asked to consent to the trackingand recording of his user behavior. The user is informed thatmaintaining the user's tracking information serves to enhance thequality and relevance of the advertisements.

One embodiment of the host server 140 includes a data mining module 270.The data mining module 270 can be any combination of software agentsand/or hardware components able to track and examine data processed bythe host server 140.

In one embodiment, the data mining module 270 includes a beacon engine275. The beacon engine 275 is configured to interact with requests fromdata miners for specific data. For example, in response to a request fordata, the beacon engine 275 may beacon the requested data for trackingpurposes, process the data into one or more reports, and deliver thereports to the data miners. The reports may be delivered by pushing thereport to the data miner through an application program interface (API)or allowing the data miner to pull the report through the API.

One embodiment of the host server 140 includes an advertiser interfacemodule 280. The advertiser interface module 280 can be any combinationof software agents and/or hardware components able to interface withmerchant POS devices and advertisers. In some embodiments, theadvertiser interface module 280 provides an interface to advertisers orlead generators such as, for example, Groupon® and Yelp®, that allowsthe advertisers to store, add, modify, and remove advertisements to andfrom the ads database 143. The advertiser interface module 280 can alsoprovide an interface to merchants via a merchant POS device and/or otherweb-accessible client devices for uploading and/or downloadingadvertisements from the database.

One embodiment of the host server 140 includes a merchant managementmodule 290. The merchant management module 290 can be any combination ofsoftware agents and/or hardware components able to interface withmerchants. The merchant management module 290 includes a POS Interface(I/F) engine 492, a web sync engine 494, an inventory engine 296, and anaccounting engine 298.

In one embodiment, the POS I/F engine 292 is configured to send and/orreceive merchant information over a communication link establishedbetween a merchant POS device and the host server 140. In some cases,the merchant management module 290 interfaces with merchant POS devicessuch that all merchant information is replicated in real-time (or closeto real-time). In some cases, the merchant POS devices act as clientdevices pushing and pulling information from the host server 140 usingthe merchant management module.

In one embodiment, the web sync engine 294 is configured to interfacewith merchant's web servers including synchronizing stored merchantinformation with the merchant's website. For example, a merchant managermay modify a menu item via a POS device. In some cases, the POS deviceincludes one or more storage containers that locally store the menuinformation; however, the menu information is also replicated to thehost server 140 for storage in the merchant database 142. Thus, when achange is made to the menu at the POS device, the menu is automaticallysaved to the merchant database 142 and the merchant web site isdynamically updated.

In one embodiment, the inventory engine 296 is configured to monitor andmanage a merchant's inventory. For example, the host server may receiveonline and/or offline itemized transaction data and automatically updatethe merchant's inventory based on these orders. Further, inventoryupdates (e.g., shipments) can be entered into the merchant POS devicefor replication and tracking purposes in the merchant database 142. Insome embodiments, the merchant POS device may include an RFID tag readercapable of reading inventory data. A more detailed description of anexample of the inventory management process in discussed with respect toFIG. 9.

In one embodiment, the accounting engine 298 is configured to trackaccounting information, perform accounting analysis, and format theaccounting information for export to various accounting software tools.

FIG. 3 depicts a block diagram illustrating an example system 300 thatfacilitates online to offline commerce, according to one embodiment. Thesystem 300 includes a network interface 310, a communications interface315, a merchant POS device 120 coupled to a reports database 144 and acustomer database 142. As shown the merchant POS 120 is the merchant POSdevice of FIG. 1; although alternative configurations are possible. Itis appreciated that the network interface 310 and the communicationinterface 315 may be similar to the network interface and communicationinterface described with respect to FIG. 2.

The merchant POS device 120, although illustrated as comprised ofdistributed components (physically distributed and/or functionallydistributed), could be implemented as a collective element. In someembodiments, some or all of the modules, and/or the functionsrepresented by each of the modules can be combined in any convenient orknown manner. Moreover, the functions represented by the modules can beimplemented individually or in any combination thereof, partially orwholly, in hardware, software, or a combination of hardware andsoftware. Furthermore, it is appreciated that some or all of themerchant POS device 120 modules described with respect to FIG. 3 may beincluded, alternatively or additionally, in whole or in part, within thehost server 140 described with respect to FIG. 2.

One embodiment of the merchant POS device 120 includes an authenticationmodule 320. The authentication module 320 can be any combination ofsoftware agents and/or hardware components able to authenticate users ofthe merchant POS device 120. In some embodiments, specific informationsuch as, for example, employee information may have restricted access tomerchant managers. Accordingly, accessing the employee information mayrequire an employee ID or password.

One embodiment of the host server 140 includes a host/manager interfacemodule 325. The host/manager interface module 325 can be any combinationof software agents and/or hardware components able to electronicallydisplay merchant information to a user of the merchant POS device andreceive input from the user.

One embodiment of the host server 140 includes an internet access module330. The internet access module 330 can be any combination of softwareagents and/or hardware components able to access the Internet and, inparticular, access merchant support information and the host server 140website.

One embodiment of the host server 140 includes a menu administrationmodule 335. The menu administration module 335 can be any combination ofsoftware agents and/or hardware components able to display, modify, andmake menu recommendations to a user of the merchant POS device.

One embodiment of the host server 140 includes a customer managementmodule 340. The customer management module 340 can be any combination ofsoftware agents and/or hardware components able to manage online andoffline customer account information and, in some cases, interact withthe host server to store this information. The customer managementmodule includes an area engine 342 and a check-in engine 344.

In one embodiment, the area engine 342 manages the location or real-timeseating arrangements of customers within the merchant facility andprovides a graphical layout for display to a user of the merchant POSdevice 120. In some cases, the locations of the customers may be brokendown by room (e.g., main dining room, bar, private rooms, etc.). Thearea engine 342 provides for graphical display of the tables and thecustomers at those tables. An example screenshot illustrating an arealayout and display is shown in FIG. 10B.

One embodiment of the host server 140 includes a merchant mobile devicemanagement module 345. The merchant mobile device management module 345can be any combination of software agents and/or hardware componentsable to communicate with and manage various merchant mobile devices(i.e., tablet handheld computers used by the wait staff and/or variouscomputers located in the merchant kitchen, bar, etc.).

One embodiment of the host server 140 includes an order processingmodule 350. The order processing module 350 can be any combination ofsoftware agents and/or hardware components able to receive, process, andmanage online and offline orders. The order processing module 350includes a POS order engine 352 and an online order engine 354.

One embodiment of the host server 140 includes a reports module 355. Thereports module 355 can be any combination of software agents and/orhardware components able to together with the host server 140 orseparately process merchant and customer data and provide variousreports to a user of the merchant POS device. In some embodiments, thereports include various analytics that may be displayed to the merchantsin any number of ways. For example, the analytics may be displayed via aplurality of panes. An example of the various panes that can be used isillustrated and discussed in more detail with respect to FIG. 14.

One embodiment of the host server 140 includes a payment processingmodule 360. The payment processing module 360 can be any combination ofsoftware agents and/or hardware components able to process payment foronline and offline orders, supplier payments, etc.

One embodiment of the host server 140 includes an employee managementmodule 365. The employee management module 365 can be any combination ofsoftware agents and/or hardware components able to manage the merchantemployee information. The merchant employee information can include, butis not limited to, schedule information, payment information,performance reports, etc.

FIGS. 4A-4B depict a flow diagram illustrating an example process 400for providing advertising recommendations to affiliated consumers andmerchants. Referring first to FIG. 4A, in process 402, the host serverreceives consumer login information. In some embodiments, the logininformation can include a customer identification (ID)/passwordcombination. In some cases, a customer can configure the mobile clientdevice to save the customer ID/password information so that the customerdoes not have to enter it each time that he/she accesses the hostserver.

In process 404, the host server determines whether the customer haslogged in via a mobile client device. If so, in process 406, locationinformation is requested and/or otherwise received from the mobileclient device. Otherwise, the host server proceeds to process 408. Inprocess 408, the host server accesses consumer data or information fromthe customer database 142. For example, the host server may access ahistory of transaction data for the consumer and/or a variety ofpreference or profile information previously determined or entered bythe customer. In process, 410, the host server accesses advertisementsusing the location and/or preference and profile information. In oneembodiment, one or more of the advertisements comprise advertisementsgenerated or suggested by the host system to reduce inventory for themerchant, increase merchant profitability, and/or drive traffic to themerchant's facility.

In process 412, one or more appropriate advertisements or promotions areidentified and electronically provided to the user. In process 414, thehost server waits for a selection of one or more of the selectedpromotions. In some cases, no promotions are selected, and the hostserver attempts to identify and provide additional promotions.

Otherwise, if a promotion is selected by a user, then in process 416,the host server determines whether the customer intends to purchase oruse the promotion online or offline. If the customer intends to use thepromotion online, then in process 418 the consumer uses the merchant webserver to buy the goods and/or services associated with promotion. Inprocess 420, the merchant web server receives payment and informationidentifying the promotion (e.g., a unique promotion number). In process422, the host server receives the transaction data information from themerchant web server. If the customer intends to use the promotionoffline, then in process 424 the consumer visits the merchant locationto buy the goods and/or services. In this case, the customer can showthe merchant the promotion which can be scanned or tracked via apromotional number. In process 426 the merchant POS receives payment andinformation identifying the promotion (e.g., a unique promotion number).In process 428, the host server receives the transaction datainformation from the merchant POS device.

Example process 400 continues in FIG. 4B. Specifically, in process 430,the host server updates the customer database to reflect the receivedtransaction data information. As previously discussed, the customer datain the customer database is used for a variety of purposes. The hostserver may also store and make available an electronic receipt for thetransaction. In process 432, the host server updates the merchantdatabase. The update to the merchant database may include a variety ofitems including merchant accounting records, inventory records, and/orupdate synchronizations to the web server. Lastly, at process 434, thehost server optionally notifies the customer that a transactionoccurred. The optional notification can transmitted to the customer viaelectronic mail, text message, voice message, etc.

FIG. 4C depicts a flow diagram illustrating an example process 450 forproviding advertising recommendations to affiliated merchants. In oneembodiment process 450 commences each time that the host server receivesonline and/or offline transaction data. However, it is appreciated thatthe example process 450 may commence or be triggered based on otherevents, periodically, etc.

In process 452, the host server receives online and/or offlinetransaction data. As previously discussed with respect to FIG. 4A, theonline and/or offline transaction data may be received from a merchantPOS device and/or a merchant web server. Other sources are alsopossible, including directly from the host server. The transaction datacan represent various information about a purchase of goods and/orservices including, in some cases, itemized lists of products purchased,prices, dates and times, locations, etc.

In process 454, the host server determines one or more merchantrecommendations. For example, in one embodiment the host serverprocesses the received transaction data to identify one or moresuggested promotions based on current inventory. As previouslydiscussed, the promotions may be later distributed to individualcustomers based on likelihood of acceptance of the promotion. In oneembodiment, the recommendations can comprise non-promotional suggestionssuch as reminders or requests, for example, to order additionalinventory, or a suggestion to price a particular menu item atrecommended value (e.g., demand-based pricing).

In process 456, the host server provides the merchant with thedetermined recommendations. In one embodiment, the recommendations areprovided via the merchant POS device. However, it is appreciated thatthe recommendations can be provided to and/or accessed by a merchantfrom any web accessible device. In process 458, the host server providesthe merchant with the recommendations. In process 460, the host serverdetermines whether one or more of the selections is selected. Lastly, ifone or more selection is made, in process 462, the host serverimplements the recommendations by making appropriate the updates. Forexample, the host server may update the Ads database for promotionsand/or update the merchant database for pricing changes.

FIG. 5 depicts a flow diagram illustrating an example process 500 forproviding host server data to affiliated advertising and/or data miningcompanies, according to an embodiment. In one embodiment, affiliateadvertisers and/or affiliate data mining companies have access to amultitude of host server data including, but not limited to, customerdata, merchant data, and advertisement data. The data can be accessedfrom the host server by the affiliate advertisers and/or the affiliatedata mining companies via one or more specific APIs.

In process 510, the host server receives login information from anaffiliated advertiser or data miner. In process 512, the host serversubsequently receives a request to push or pull data from the hostsystem. In process 514, the host server determines whether the requesteddata is allowed for that particular advertiser and/or data miner. Insome embodiments, levels of access can be tiered based on an agreement.However, some identifying data may never be accessible to theadvertisers and/or data miners. Further, in some cases, data is pushedor pulled in the form of a report.

In process 516, the host server beacons the data for tracking purposes.For example, data may be tracked for specific events. In process 518,the host server generates one or more data reports, and in process 520,provides the reports to the advertiser and/or data miner. Lastly, inprocess 522, the host server facilitates payment or credit, ifnecessary. For example, depending on the agreement, advertisers and/ordata miners may be charged or credited for pushing or pulling data fromthe host server.

FIG. 6 depicts a block diagram of an online environment 600 suitable forfacilitating online to offline commerce, according to an embodiment.FIG. 6 provides a more detailed example of environment 100.Specifically, in FIG. 6, the merchant comprises a bar or restaurant;however, alternate configurations are possible.

Environment 600 includes an affiliate restaurant, an affiliate merchantweb server, a host server, and a wireless base station all connected viaa network. The host server may be host server 140 of FIG. 1; althoughalternative configurations are possible. The affiliate restaurantincludes a restaurant POS device operated by a restaurant host and/ormanager, a first food server A operating a first mobile merchant device(e.g., a tablet computer), a second food server B operating a secondmobile merchant device (e.g., a tablet computer), and a first person Aoperating a mobile client device (e.g., smart phone device). Inaddition, environment 600 includes a second person B operating a mobileclient device (e.g., smart phone device) in communication with thewireless base station and a third person C operating a non-mobile clientdevice via Cable or DSL or other known connectivity schemes.

In one embodiment, person A can check-in to the affiliate restaurant viathe wireless base station or the local WiFi hotspot at the restaurant.Once checked in, person A can access, view, and pay for his or her billusing the mobile client device. The host server facilitates thiscommunication and in one or more embodiments all data requests andresponses that traverse the system travel though the host server. Inother embodiments, the host system facilitates a direct communicationbetween person A's mobile client device and the restaurant POS device.The direct communication may traverse the network, but does not have to.An example of the check-in process is discussed in more detail withrespect to FIG.

In one embodiment, either person B or person C can remotely purchasegoods and/or services for person A when person A checks—in at therestaurant. In some embodiments, person B and/or person C are notifiedthat person A checked-in at the restaurant via a shared social network.An example of social online buying is discussed in more detail withrespect to FIGS. 8A-8B.

FIG. 7 depicts a flow diagram illustrating example process 700 forrequesting real-time pre-sale transaction data (e.g., pre-bill) using amobile client device in an online environment suitable for facilitatingonline to offline commerce, according to an embodiment. The exampleprocess 700 is described with reference to environment 600 of FIG. 6,although other configurations are possible.

In process 710, customer A notices or is notified that the merchanthe/she is patronizing provides host services. For example, in oneembodiment, customer A may log into the host server and search for themerchant by name. Alternatively or additionally, the mobile clientdevice operated by customer A may provide location information to thehost server allowing the host server to notify the user about theability to “check-in” at the merchant location. In one embodiment,customer A “checks-in” at the merchant location and subsequently noticesor is notified about the services that the merchant supports (e.g.,“check-in,” “mobile-view and pay,” and/or “mobile order, view, andpay”).

In process 712, customer A “checks-in” at the merchant location via thehost server using a mobile client device. As previously discussed, themobile client devices may be modified to include additional hardwareand/or software to facilitate the online to offline commerce. In oneembodiment, customer A “checks-in” at the merchant location via a mobiledata network. In this case, all data transferred between the merchantPOS device and customer A traverses the wireless base station shown inFIG. 6. In one embodiment, customer A accesses the internet via an openWiFi network at the merchant facility.

Once checked-in at the merchant location, the host server may providecustomer A with the mobile capabilities of the merchant. For example,the merchant may allow a customer to “check-in and view their bill,”“check-in, view, and pay” for their bill, or “check-in view, modify, andpay for their bill.” The capabilities may be displayed to the user onthe mobile client device. In this example, the merchant provides forview/modify capabilities, and thus, in process 714, customer A requeststo view/modify the check or bill at the merchant using portableelectronic device.

In process 716, the host system forwards the request to the merchant POSdevice. In process 718, the merchant POS processes the request toview/modify the check and associates the request with a customer. In oneembodiment, associating the request with the customer further comprisesconfirming that the customer requested to view/modify the check. Oncethe request is processed, in process 712, the merchant POS devicenotifies customer A that the request to view/modify has been accepted,modifies the check to reflect an order (if necessary), and forwards thecheck (pre-bill) to customer A, as indicated in process 720.

It is appreciated that customer A can then modify the check (pre-billtransaction data) any number of times before ultimately paying via themobile client device. As previously discussed, the host serverfacilitates payment. In one embodiment, the host server provides fund tothe merchant and debits customer A's account. In another embodiment, thehost server transfers payment instructions (e.g., credit card, etc.) tothe merchant POS device for payment.

FIGS. 8A and 8B depict a flow diagram illustrating example process 800of social online ordering in an online environment suitable forfacilitating online to offline commerce, according to an embodiment. Asdiscussed herein, the process of social online ordering allows onlinefriends of a customer that has checked-in to a merchant location toremotely purchase goods and/or services for that checked-in customer.

In process 810, person A notices or is notified that the merchant he/sheis patronizing provides host services. For example, in one embodiment,person A may log into the host server and search for the merchant byname. Alternatively or additionally, the mobile client device operatedby person A may provide location information to the host server allowingthe host server to notify the user about the ability to “check-in” atthe merchant location.

In process 812, person A “checks-in” at the merchant location via thehost server using a mobile client device. As part of the check-inprocess, the mobile client device may provide location information toverify location and establish which of the merchant's locations person Ais checking in to in the event that the merchant has more than onelocation. In process 814, the host sever updates person A'sstatus/location via one or more social networks. As previouslydiscussed, a user can specify one or more social web server to check-into during the check-in process. Alternatively or additionally, person Amay provide the check-in information (including which social servers tocheck-in to and login credentials) in a user profile. Upon receiving theupdates, the social web servers post person A's updates to, for example,one or more social feeds.

In process 816, person B and person C are notified of person A's updatedlocation and status via, for example social feeds provided by the socialweb server. In response to receiving this notification or otherwiseidentifying person A's updated status, in process 820, person C logs into the host server by providing the host server with login credentials.In process 822, person C orders a gift of goods and/or services forPerson A at the merchant location. In process 824, the host systemnotifies person A of the gift.

Continuing the example process 800 to FIG. 8B, in process 826, the hostserver identifies whether or not person A accepts the gift at themerchant location. If so, in process 828, the host system notifies themerchant of the purchase. For example, the host system may send uniquegift identification information to the merchant POS device. In process830, the host system notifies person C of acceptance of the gift. In oneembodiment, when person A accepts the gift, person A can enter apersonal thank you message (e.g., voice or text based), which is sent toperson C with the notification.

In process 832, to redeem the gift, person A shows a coupon or code tothe merchant. In one embodiment, the merchant POS device or a merchantmobile device in communication with the merchant POS device can receivethe couple via Bluetooth, and/or can scan the coupon via a bar codescanner. In process 834, the merchant POS device identifies the validityof the coupon or code by looking up it up in the system. In process 836,the merchant POS device determines if there is a match. If there is nomatch, then in process 844, the merchant POS device notifies that thereis no match. If there is a match, then in process 838, the merchant POScommunicates order fulfillment to the host system. In process 840, thehost system charges person C. In process 842, the host serverfacilitates payment to the merchant.

If person A does not accept the gift at the merchant location, then inprocess 850, the host system determines whether person A wants to bankthe gift. For example, person A may not want the beer that person Cbought for them right now or may already have a beer that person Cbought via a remote mobile device. Accordingly, if person A wants tobank the gift (i.e., add money to an account on the host server), thenin process 852, the host system charges person C, and in process 854,credits person A's account which can be applied to meals at the currentmerchant's location and/or any other affiliate merchant's location.However, if person A does not want to accept the gift and does not wantto bank the gift, then in process 856 notifies person C of therejection.

FIG. 9 depicts a sequence diagram 900 illustrating an example ofinventory management in an online environment suitable for facilitatingonline to offline commerce, according to an embodiment. In particular,FIG. 9 illustrates how merchant inventory and/or a merchant website canbe automatically updated. The example sequence diagram 900 is describedwith reference to environment 600 of FIG. 6, although otherconfigurations are possible.

The series of sequences at 910 illustrate an example of a merchant POSdevice transmitting inventory update information to a host server. Theinventory information may be transferred as backup or the host servermay be the sole source of the information. In addition, the inventoryupdate may be transmitted in response to new inventory arriving at themerchant location, new inventory being entered into the merchant POSdevice, etc. Responsive to receiving the update, the host server updatesthe inventory and stores the information in the merchant database.Additionally, the inventory update may automatically be synced to theweb server. For example, in one embodiment, when seasonal inventory isupdated at the host server, the host server may have instructions fromthe merchant to automatically update the website. The website may beupdated to indicate the inventory or the menu may be updated to indicatethat seasonal dishes are now available.

The series of sequences at 920 illustrate an example of an incrementalinventory updates that occur due to offline purchases. To begin, anoffline purchase or order is taken by a server using a merchant mobiledevice at the restaurant. The merchant mobile device passes the orderinformation to the merchant POS device and the merchant POS deviceforward the transaction data to the host server. The transaction datamay be pre- or post-sale. However, for real-time inventory updates,pre-sale information provides a more accurate view of real-timeinventory. Responsive to receiving the update, the host server updatesthe inventory and stores the information in the merchant database.Additionally, the inventory update may automatically be synced to theweb server.

The series of sequences at 930 illustrates an example of an incrementalinventory updates that occur due to social online purchases. To begin,an online purchase or order is received at the web server from person B(e.g., to order a beer for person A, for example). The web serverforwards the transaction data to the host server. The host serverforwards the order to the merchant POS for ultimate approval andfulfillment. When a fulfillment message is received by the host server,the host server adjusts the inventory and syncs up appropriate websiteinventory.

The series of sequences at 940 illustrate an example of an autoinventory order. The host server may periodically, after every order, orafter some other triggering event, compare the inventory to a threshold.If the inventory falls below the threshold, the host server triggers anotification to the merchant, and in some cases, an auto order. Amerchant can set up auto order instructions in the host server. In somecases, the merchant may request to first receive an authorizationrequest with the notification. However, in other cases the authorizationrequest is not required.

FIGS. 10A-10C depict example user interfaces illustrating the process ofoperating a point of sale device, according to an embodiment. Referringfirst to FIG. 10A which illustrates an example of a merchant POS device“home” or intro interface 1000A. In this example, the merchant POSdevice interface 1000A includes a status pane 1005 and a primary pane1010. The status pane 1005 includes a “Leapset” logo, a welcome message1006, and a sign out button 1008. When logged in, the welcome message1006 provides a message to the user logged in to the host server. Inthis example, “Hi, Dave. C.,” is displayed because Dave C. is currentlylogged in to the host server.

In this example, the primary pane 1010 includes a variety of touchactivated buttons including: a point of sale button 1012, an onlineorders button 1014, a customer button 1016, a menu button 1018, anemployee button 1020, a reports button 1022, a support button 1024, aleapset.com button 1026, and a sign in button 1028. Touching any one ofthe buttons takes the user to a new screen that provides moreinformation.

FIG. 10B illustrates an example of a merchant POS device POS interface1000B. The merchant POS device will display the POS interface 1000B if,for example, a user touches the point of sale button 1012 in FIG. 10A.The POS interface 1000B includes a status pane and a primary panesimilar to FIG. 10A. The primary pane includes buttons panel 1030,seating arrangement area 1040, customer check-in area 1050, and an orderpane 1060.

Button panel 1030 includes buttons 1032-1038 with each button providingthe described functionality when touched. For example button 1032 allowsa user of the merchant POS device to view an orders screen and buttons1034-1038 allow a user to manipulate the tables and rooms in seatingarrangement area 1040. The seating arrangement area 1040 includes tabs1042-1046 to switch between various rooms that can be created by viabutton 1038. Each room includes a variety of tables 1048 that can becreated via button 1036 and merged via button 1034. Customers that havechecked-in are indicated by graphics 1049 at the table 1048 at whichthey are seated. Each table may indicate whether people are seated atthe table, and if so, how many.

A customer check-in area 1050 illustrates more information about thecustomers that have checked-ion. A profile button allows a user to viewthe profiled of any customer that has checked-in. The profileinformation may include order history, likes/dislikes, specialinstructions/needs, etc. Additional information such as, for example,last visit, number of visits, and favorite items may also be displayed.

The order pan 1060 includes various status buttons including a new orderbutton 1062, a pending order button 1064, and an open order button 1066.The pending order button 1064 indicates the number of pending orders(e.g., those orders that have been received but not yet approved by themerchant) and the open order button 1066 indicates the number of openorders (e.g., orders received and approved). Touching either buttontakes the user to a more detailed screen illustrating the respectivepending (FIG. 11E) or open (FIG. 11G) orders.

FIG. 10C illustrates an example of a merchant POS device POS interface1000C. The merchant POS device will display the POS interface 1000C if,for example, a user touches table 5 on FIG. 10B. FIG. 1000C providesadditional details about the individuals and order associated with table5. In addition, controls are provided to for payment and returning toother interfaces.

FIGS. 11A-10H depict example user interfaces illustrating the process ofonline ordering from the perspective of a mobile client device and apoint of sale device, according to an embodiment.

Referring first to FIGS. 11A-C which illustrate examples of the mobileonline ordering interface 1100A, 1100B, and 1100C, respectively. Whenusing the mobile online interface, a user must first login to the hostserver using a mobile client device. In the example of FIGS. 11A, 11B,and 11C, the user or customer has identified a Leapset affiliaterestaurant called “Ike's Lair.” As shown, a user can browse menu items,order, enter special instructions, and make a purchase using the mobileonline ordering interfaces 1100A, 1100B, and 1100C.

FIGS. 11D and 11E illustrate examples of the merchant POS deviceinterfaces 1100D and 1100E, when an online order is received (e.g., theorder place in FIG. 11C). A user of the merchant POS device can acceptthe order and begin processing the order or snooze the acceptance of theorder for some period of time (e.g., if busy processing an offlineorder). If an order is accepted via merchant POS device interface 1100D,then the new online order becomes a pending order.

In some embodiments, pending orders can still be approved or rejected asshown in merchant POS device interface 1100E. FIG. 11F illustrates anexample of the mobile online ordering interface 1100F displayed to acustomer once the order has been accepted by the merchant. FIG. 11Gillustrates an example of the merchant POS device interface once apending order has been accepted. In once pending orders are accepted,they become open orders. Once an open order is ready a user of themerchant POS device interface hits the “order ready” button and anotification is sent to the online mobile user.

FIG. 11H illustrates an example of the mobile online ordering interface1100H that displayed to a customer on the mobile client device when theuser's order is ready. The mobile client device receives a notificationwhen the order is ready. In response to receiving the notification, themobile client device displays the mobile online ordering interface 1100Hwhich, in some embodiments, provides a user with a directions buttonallowing the user to calculate directions to the restaurant from acurrent location.

FIGS. 12A-12J depict example user interfaces illustrating the process ofchecking in via the in-store experience from the perspective of a mobileclient device and a point of sale device, according to an embodiment.Referring first to FIGS. 12A and 12B which illustrate examples of themobile online ordering interface 1200A, and 1200B, respectively. In oneexample, when a user logs onto the host server or launches the hostserver application on a mobile client device, the mobile online orderinginterface 1200A is displayed. The mobile online ordering interface 1200Aincludes a plurality of buttons, a search engine, an account button totake the user to his/her personal account, and a pay button. Moreover,some or all of the mobile online ordering interfaces, includinginterface 1200A, include a footer bar including, for example, thefollowing button: home, nearby places, search, check-in, and purchase.The main pane of the mobile online ordering interface 1200A alsoincludes buttons for nearby locations, online ordering, account,check-in pay, local deals, and purchases (e.g., history).

In one example of operation, the check-in button will be highlightedwhen a user is at a merchant that provides for host services. If acustomer chooses to check-in to a merchant location by selecting thecheck-in button or check-in pay button, then the mobile online orderinginterface 1200B is displayed. The mobile online ordering interface 1200Ballows a user to provide a status update (e.g., comments) and choosefrom a variety of social networks to check-in (e.g., via slidebarbuttons). When ready, the customer selects the “check-in here” button.

FIG. 12C illustrates an example of social feeds 1200C. In particular,the customer's friends may see, for example, social feeds 1200C in theirsocial network feeds after a customer has checked-in at a merchantlocation. FIG. 12D illustrates an example of a merchant POS device POSinterface 1200D. POS interface 1200D illustrates the interface displayedon the merchant POS device after the customer has checked-in. As shownin FIG. 12E, a user of the of a merchant POS device can select a tablewhen a customer checks-in. Further, in some embodiments, customers thathave checked-in but are not seated in the seating area can be seated inthe order in which they checked-in. At seating, the user of the merchantPOS device can move the checked-in user to a table. FIG. 12F illustratesan example of a merchant POS device interface 1200F with an indicator attable 5 that a checked-in customer is sitting there after having beenmoved to the table.

FIG. 12G illustrates an example of a merchant POS device interface 1200Gshowing profile information of a customer. The profile information canbe displayed on the merchant POS device interface by, for example,selected the “view profile” button in the customer check-in area of FIG.12F. Alternatively or additionally, the profile information can beviewed by selecting the “customers” button on the main or home page(e.g., FIG. 10A).

FIG. 12H illustrates an example of a merchant POS device interface 1200Hshowing table level information (e.g., table 5). A letter or envelopenext to a customer may indicate that this party has checked-in to view,modify and/or view, modify, and pay the bill. FIGS. 12I-12J illustratean example of mobile client device interfaces 12001 and 1200)illustrating the process and ability to view and pay for the bill viathe mobile client device. For example, a mobile customer may view anitemized list, add tip, pay, email the receipt, and/or print thereceipt.

FIGS. 13A-13E depict example user interfaces illustrating the process ofsocial ordering from the perspective of mobile client device, the onlinesocial ordering device, and a merchant point of sale device, accordingto an embodiment.

FIG. 13A illustrates an example user interface illustrating the processof checking in via the in-store experience from the perspective of amobile client device. As previously discussed, the user of the mobileclient device can enter comments and select one or more social webnetworks on which to check-in (i.e., share status and/or locationinformation). FIG. 13B illustrates an example of one of the sharedsocial feeds 1300C. In this case, there is also a “Buy Rex a beer!” linkthat allows an online friend of Rex's follow the link and commence asocial order for a friend. If a friend does clicks on the link, they maybe taken to the host server web interface where they are presented witha menu of options as shown in FIG. 13C.

FIG. 13D illustrates an example user interface illustrating the messagethat the checked-in party (e.g., Rex) receives from the perspective of amobile client device. As previously discussed, the user of the mobileclient device can accept, decline, or bank card (or simply bank) thegift. FIG. 13E illustrates an example user interface illustrating theindication received at the merchant point of sale device. In someembodiments, the merchant will only receive this notification if thegift is accepted at the merchant location.

FIG. 14 depicts an example user interfaces illustrating a sampleanalytics report 1400 displayed on a point of sale device, according toan embodiment. A user of a merchant point of sale device may accessreports by selecting the reports button on the home or main menu shownin FIG. 10A. A variety of analytics may be available to merchants. Forexample, sales, inventory, customers, forecasts, employees, andpromotions may be analyzed and reports generated by the host server forenhanced comprehension.

FIG. 15 depicts an example user interfaces illustrating the process ofoffline (in-store) ordering from the perspective of the merchant mobiledevices, according to an embodiment. It is appreciated that eachmerchant may have any number of mobile management device incommunication with the host server, or in some cases, none at all.

FIG. 16 shows a diagrammatic representation of a machine in the exampleform of a computer system 1600 within which a set of instructions, forcausing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed.

In alternative embodiments, the machine operates as a standalone deviceor may be connected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in a client-server network environment, or as a peermachine in a peer-to-peer (or distributed) network environment.

The machine may be a server computer, a client computer, a personalcomputer (PC), a tablet PC, a set-top box (STB), a personal digitalassistant (PDA), a cellular telephone or smart phone, a tablet computer,a personal computer, a web appliance, a point of sale device, a networkrouter, switch or bridge, or any machine capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine.

While the machine-readable (storage) medium is shown in an exemplaryembodiment to be a single medium, the term “machine-readable (storage)medium” should be taken to include a single medium or multiple media(e.g., a centralized or distributed database, and/or associated cachesand servers) that store the one or more sets of instructions. The term“machine-readable medium” or “machine readable storage medium” shallalso be taken to include any medium that is capable of storing, encodingor carrying a set of instructions for execution by the machine and thatcause the machine to perform any one or more of the methodologies of thepresent invention.

In general, the routines executed to implement the embodiments of thedisclosure, may be implemented as part of an operating system or aspecific application, component, program, object, module or sequence ofinstructions referred to as “computer programs.” The computer programstypically comprise one or more instructions set at various times invarious memory and storage devices in a computer, and that, when readand executed by one or more processors in a computer, cause the computerto perform operations to execute elements involving the various aspectsof the disclosure.

Moreover, while embodiments have been described in the context of fullyfunctioning computers and computer systems, those skilled in the artwill appreciate that the various embodiments are capable of beingdistributed as a program product in a variety of forms, and that thedisclosure applies equally regardless of the particular type of machineor computer-readable media used to actually effect the distribution.

Further examples of machine or computer-readable media include but arenot limited to recordable type media such as volatile and non-volatilememory devices, floppy and other removable disks, hard disk drives,optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), DigitalVersatile Disks, (DVDs), etc.), among others, and transmission typemedia such as digital and analog communication links.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense; that is to say, in the sense of“including, but not limited to.” As used herein, the terms “connected,”“coupled,” or any variant thereof, means any connection or coupling,either direct or indirect, between two or more elements; the coupling ofconnection between the elements can be physical, logical, or acombination thereof. Additionally, the words “herein,” “above,” “below,”and words of similar import, when used in this application, shall referto this application as a whole and not to any particular portions ofthis application. Where the context permits, words in the above DetailedDescription using the singular or plural number may also include theplural or singular number respectively. The word “or,” in reference to alist of two or more items, covers all of the following interpretationsof the word: any of the items in the list, all of the items in the list,and any combination of the items in the list.

The above detailed description of embodiments of the disclosure is notintended to be exhaustive or to limit the teachings to the precise formdisclosed above. While specific embodiments of, and examples for, thedisclosure are described above for illustrative purposes, variousequivalent modifications are possible within the scope of thedisclosure, as those skilled in the relevant art will recognize. Forexample, while processes or blocks are presented in a given order,alternative embodiments may perform routines having steps, or employsystems having blocks, in a different order, and some processes orblocks may be deleted, moved, added, subdivided, combined, and/ormodified to provide alternative or subcombinations. Each of theseprocesses or blocks may be implemented in a variety of different ways.Also, while processes or blocks are at times shown as being performed inseries, these processes or blocks may instead be performed in parallel,or may be performed at different times. Further any specific numbersnoted herein are only examples: alternative implementations may employdiffering values or ranges.

The teachings of the disclosure provided herein can be applied to othersystems, not necessarily the system described above. The elements andacts of the various embodiments described above can be combined toprovide further embodiments.

Any patents and applications and other references noted above, includingany that may be listed in accompanying filing papers, are incorporatedherein by reference. Aspects of the disclosure can be modified, ifnecessary, to employ the systems, functions, and concepts of the variousreferences described above to provide yet further embodiments of thedisclosure.

These and other changes can be made to the disclosure in light of theabove Detailed Description. While the above description describescertain embodiments of the disclosure, and describes the best modecontemplated, no matter how detailed the above appears in text, theteachings can be practiced in many ways. Details of the system may varyconsiderably in its implementation details, while still beingencompassed by the subject matter disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the disclosure should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the disclosure with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the disclosure to the specific embodimentsdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe disclosure encompasses not only the disclosed embodiments, but alsoall equivalent ways of practicing or implementing the disclosure underthe claims.

While certain aspects of the disclosure are presented below in certainclaim forms, the inventors contemplate the various aspects of thedisclosure in any number of claim forms. For example, while only oneaspect of the disclosure is recited as a means-plus-function claim under35 U.S.C. §112, ¶6, other aspects may likewise be embodied as ameans-plus-function claim, or in other forms, such as being embodied ina computer-readable medium. (Any claims intended to be treated under 35U.S.C. §112, ¶6 will begin with the words “means for”.) Accordingly, theapplicant reserves the right to add additional claims after filing theapplication to pursue such additional claim forms for other aspects ofthe disclosure.

What is claimed is:
 1. A method of facilitating commerce, comprising:receiving, at a management system and from a first mobile client deviceof a first customer, a request to check-in at a merchant facility;receiving, at the management system and from the first mobile clientdevice of the first customer, a request to access real-time pre-saletransaction data associated with the first customer; processing, at themanagement system, the request to access real-time pre-sale transactiondata, said processing including: responsively accessing the real-timepre-sale transaction data from a point of sale (POS) device locatedproximate the first mobile client device at the merchant facility, thereal-time pre-sale transaction data including an itemized pre-bill forgoods and/or services provided by the merchant facility; andtransmitting, at the management system, the real-time pre-saletransaction data to the first mobile client device for display to thefirst customer; transmitting, at the management system, a status updatemessage to a set of social networking servers associated with a set ofsocial networks of the first customer, the status update messagenotifying a set of users associated with the set of social networks thatthe first customer has checked-in at the merchant facility; receiving,at the management system and from a second mobile client device of asecond customer, an order request to modify an item of goods and/orservices associated with the itemized pre-bill included in the real-timepre-sale transaction data, the second customer being a user of the setof users associated with at least one of the set of social networks ofthe first customer, wherein the order request to modify comprises arequest to pay for the item of goods and/or services at the merchantfacility for the first customer; responsive to the order requestreceived from the second customer, transmitting, at the managementsystem, the order request to the first mobile client device for approvalby the first customer; and in an event the first customer approves theorder request: modifying the item of goods and/or services based on theorder request; and transmitting, at the management system and to the POSdevice, the order request for fulfillment by the merchant facility. 2.The method of claim 1 further comprising: authenticating, at themanagement system, the request to check-in using identification dataassociated with the first customer; and in response to successfulauthentication, sending, at the management system, a confirmation to thefirst mobile client device.
 3. The method of claim 1, wherein the orderrequest to modify further comprises: a request to order a gift of goodsat the merchant facility for the first customer, the gift of goods beinga new item of goods associated with the itemized pre-bill; or a requestto order a gift of services at the merchant facility for the firstcustomer, the gift of services being a new item of services associatedwith the itemized pre-bill.
 4. The method of claim 1, wherein the firstmobile client device and the point of sale device are located at themerchant facility.
 5. A management system comprising: a networkinterface configured to: receive, from a first mobile client device of afirst customer, a request to check-in at a merchant facility and arequest to access real-time pre-sale transaction data associated withthe first customer; authenticate the request to check-in at the merchantfacility; process the request to access the real-time pre-saletransaction data; transmit, to the first mobile client device, thereal-time pre-sale transaction data associated with the first customer,the real-time pre-sale transaction data including an itemized pre-billfor goods and/or services provided by the merchant facility; transmit,to a set of social networking servers associated with a set of socialnetworks of the first customer, a status update message notifying a setof users associated with the set of social networks that the firstcustomer has checked-in at the merchant facility; receive, from a secondmobile client device of a second customer, an order request to modify anitem of goods and/or services associated with the itemized pre-billincluded in the real-time pre-sale transaction data, the second customerbeing a user of the set of users associated with at least one of the setof social networks of the first customer, wherein the order request tomodify the item of goods and/or services comprises a request to pay forthe item of goods and/or services at the merchant facility for the firstcustomer; transmit, to the first mobile client device of the firstcustomer, the order request for an approval by the first customer; in anevent the first customer approves, forward, to the POS device, the orderrequest for fulfillment by the merchant facility; and a processingsystem comprising: a processor configured to: responsively access thereal-time pre-sale transaction data from a point of sale (POS) devicelocated at the merchant facility for transmission to the first mobileclient device of the first customer; obtain the approval for the orderrequest from the first customer via the first mobile client device; andmodify the item of goods and/or services based on the order request. 6.The management system of claim 5, the network interface furtherconfigured to, in response to successful authentication, transmit acheck-in confirmation to the first mobile client device, the check-inconfirmation indicating that the first customer has successfullychecked-in at the merchant facility.
 7. The management system of claim5, wherein the order request to modify the real-time pre-saletransaction data further comprises: a request to order a gift of goodsat the merchant facility for the first customer, the gift of goods beinga new item of goods associated with the itemized pre-bill; or a requestto order a gift of services at the merchant facility for the firstcustomer, the gift of services being a new item of services associatedwith the itemized pre-bill.
 8. A non-transitory computer-readable mediumstoring computer-executable instructions for implementing a method,comprising: instructions for receiving, from a first mobile clientdevice of a first customer, a request to check-in at a merchantfacility; instructions for receiving, from the first mobile clientdevice of the first customer, a request to access real-time pre-saletransaction data associated with the first customer; instructions forprocessing the request to access real-time pre-sale transaction data,said instructions for processing including: instructions forresponsively accessing the real-time pre-sale transaction data from apoint of sale (POS) device located proximate the first mobile clientdevice, the real-time pre-sale transaction data including an itemizedpre-bill for goods and/or services provided by the merchant facility;and instructions for transmitting the real-time pre-sale transactiondata to the first mobile client device for display to the firstcustomer; instructions for transmitting a status update message to a setof social networking servers associated with a set of social networks ofthe first customer, the status update message notifying a set of usersassociated with the set of social networks that the first customer haschecked-in at the merchant facility; instructions for receiving, from asecond mobile client device of a second customer, an order request tomodify an item of goods and/or services associated with the itemizedpre-bill included in the real-time pre-sale transaction data, the secondcustomer being a user of the set of users associated with at least oneof the set of social networks of the first customer, wherein the orderrequest to modify comprises a request to pay for the item of goodsand/or services at the merchant facility for the first customer;instructions for responsive to the order request received from thesecond customer, transmitting the order request to the first mobileclient device for approval by the first customer; and instructions for,in an event the first customer approves the order request: modifying theitem of goods and/or services based on the order request; andtransmitting, to the POS device, the order request for fulfillment bythe merchant facility.
 9. The non-transitory computer-readable medium ofclaim 8, further comprising: instructions for authenticating the requestto check-in using identification data associated with the firstcustomer; and instructions for, in response to successfulauthentication, sending a confirmation to the first mobile clientdevice.
 10. The non-transitory computer-readable medium of claim 8,wherein the order request to modify further comprises: a request toorder a gift of goods at the merchant facility for the first customer,the gift of goods being a new item of goods associated with the itemizedpre-bill; or a request to order a gift of services at the merchantfacility for the first customer, the gift of services being a new itemof services associated with the itemized pre-bill.
 11. Thenon-transitory computer-readable medium of claim 8, wherein the firstmobile client device and the POS device are located at the merchantfacility.